Hi all, I have a dilema that I hope someone can assist me with. I have User A transfer departments, one of my help desk techs deleted her AD account (which disconnected her mailbox) and recreated the account. They didn't know that they could reconnect the old mailbox so they created a new mailbox. I created an archive AD account and I am trying to connect her old mailbox to it but it is giving me the following error message. "Summary: 1 item(s). 0 succeeded, 1 failed. Elapsed time: 00:00:00 Maria Jurado Failed Error: The LegacyExchangeDN "/O=LACARE/OU=EXCHANGE ADMINISTRATIVE GROUP (FYDIBOHF23SPDLT)/CN=RECIPIENTS/CN=MARIAJ" of "da4fdcca-35c4-4cbd-8983-b66f7042eedf" is being used by the following user in Active Directory: "Maria Jurado". The value for LegacyExchangeDN must be unique to each user. Exchange Management Shell command attempted: Connect-Mailbox -Identity 'da4fdcca-35c4-4cbd-8983-b66f7042eedf' -Database 'MAILBOXCLUSTER.lacare.org\SGTier1-03\DBTier1-03' -User 'lacare\mariajarc' -Alias 'mariajarc' Elapsed Time: 00:00:00 Not sure why I am getting this error message. Any insight would be greatly appreciated. Thank you Gladys

Hi,That's the default behaviour. Please understand that the relevant Exchange attributes (LegacyExchangeDN) is still existing on the Mailbox Object after deleting the AD account.As all known, mailbox contains of an AD user and the mailbox data. When you create the mailbox for a user, the Exchange attributes that are required for a mailbox are added to the user object in Active Directory. When you disable or delete the user account, the Exchange attributes are cleared from the AD user which make the AD user disconnect mailbox object (mailbox data), but the relevant Exchang attributes always being there.Since the help desk recreated the account which has the same name as the original user, the current LegacyExchangeDN is also same as the original mailbox. When you reconnect the original mailbox (disconnected mailbox) to the new user account, the original LegacyExchagneDN (Exchange attributes) on the Mailbox Object will be assigned into this new user accout. That cause the LegacyExchangeDN to be conflicted.Thus, please delete the mailbox or user account which created by the help desk. Then reconnect it again.ThanksAllen

Thank you for your input.

Hi, There is second option too, u can change LegacyExchangeDN of the mailbox user which help desk created using ADSIEdit tool,and then connect the disconnected mailbox in the same way as u are trying, it will then not conflict the LegacyExchangeDN attribute. I have done this at couple of times. Regards,Laeeq Qazi|Team Lead(Exchange + Sharepoint + BES + DynamicsCRM) www.HostingController.com

On Sat, 20 Feb 2010 22:58:22 +0000, Laeeq Qazi wrote:>Hi, There is second option too, u can change LegacyExchangeDN of the mailbox user which help desk created using ADSIEdit tool,and then connect the disconnected mailbox in the same way as u are trying, it will then not conflict the LegacyExchangeDN attribute. I have done this at couple of times. Regards,>Laeeq Qazi|Team Lead(Exchange + Sharepoint + BES + DynamicsCRM) www.HostingController.com Changing the LDN value of the current user means that any replies sentto messages sent by that mailbox will either be returned asundeliverable or get dumped into the mailbox you're trying to recover-- and that just the least of the problems you'll cause for thatperson.It's safer to disconnect the active (new) mailbox from the (new) user,then reconnect the (old) mailbox you want to recover to some otheruser account. Then reconnect the new mailbox to the new user.---Rich MatheisenMCSE+I, Exchange MVP--- Rich Matheisen MCSE+I, Exchange MVP

Hi, Both the new malbox and the disconnected mailbox have identical LegacyExchangeDNs. If we dont modify the LegacyExchangeDN of the current (new) mailbox then there will always be a conflict when u will try to reconnect the one of disconnected mailbox. Also if we disable the current mailbox or delete it so that we could enable (reconnect the original mailbox) then u will have problem in reconnecting this new mailbox again because their LegacyExchangeDNs are same, u havent changed it. So avoiding this fuss I have proposed to modify the LegacyExchangeDN of the current (new) mailbox so that original (old) mailbox could be restored using the original LegacyExchangeDN, and u dont have the need to disable or delete the new mailbox in this case. Also as far as replies to sent emails of new mailbox is concerned then this could be a problem but as the O.P has said that its a new mailbox so I hope that there will be little problem in this case. And final point;its better to modify the legacyDN instead of Deleting the new mailbox or disabling it, which will be of no use. Also both (new+old) mailboxes belong to single User (as far as I understand the query of O.P), so if emails sent to one are received in the inbox of second one then it will not be a problem. Regards, Laeeq Qazi|Team Lead(Exchange + Sharepoint + BES + DynamicsCRM) www.HostingController.com

On Mon, 22 Feb 2010 09:28:16 +0000, Laeeq Qazi wrote:>Hi, Both the new malbox and the disconnected mailbox have identical LegacyExchangeDNs. Yes, they do.>If we dont modify the LegacyExchangeDN of the current (new) mailbox then there will always be a conflict when u will try to reconnect the one of disconnected mailbox. Nope. That's true only if one of them is connected to a user. If BOTHare disconnected then either of them can be connected to the user.>Also if we disable the current mailbox or delete it so that we could enable (reconnect the original mailbox) then u will have problem in reconnecting this new mailbox again because their LegacyExchangeDNs are same, u havent changed it. True. I omitted a step.1. Disconnect the current (new) mailbox from the real user.2. Connect the current (new) mailbox to a temporary user.3. Change the LDN on the temporary user.4. Connect the disconnected (old) mailbox to the real user.Now the real user has the correct LDN. You can use ExMerge to combinethe contents of the mailbox connected to the temporary user with themailbox connected to the real user. And, because the real user hasretained the LDN there will be no problems with NDRs or permissions.>So avoiding this fuss I have proposed to modify the LegacyExchangeDN of the current (new) mailbox so that original (old) mailbox could be restored using the original LegacyExchangeDN,Which means that the real user now has a different LDN. That's not adesirable result.>and u dont have the need to disable or delete the new mailbox in this case. Also as far as replies to sent emails of new mailbox is concerned then this could be a problem but as the O.P has said that its a new mailbox so I hope that there will be little problem in this case. It's hard to say, isn't it? I think it's better to keep the LDN withthe right user and avoid guesswork.>And final point;its better to modify the>legacyDN instead of Deleting the new mailbox or disabling it, which will be of no use. Oh, I think it will be of great use.>Also both (new+old) mailboxes belong to single User (as far as I understand the query of O.P), The CONTENTS of the TWO mailboxes "belong" to the same person, but youhave two mailboxes in the database and two users in the AD. In thiscase a "person" and a "user" are not identical.>so if emails sent to one are received in the inbox of second one then it will not be a problem.If the only use of the LDN was the delivery of mail I might agree. Butthe LDN is associated with any other uses, one of which is theidentification of the Free/Busy information. Since the release ofExchange wasn't mentioned it's quite possible that the F/B info isavailable only in public folders. If that's true then the LDN ispretty important. Regards, >Laeeq Qazi|Team Lead(Exchange + Sharepoint + BES + DynamicsCRM) www.HostingController.com ---Rich MatheisenMCSE+I, Exchange MVP--- Rich Matheisen MCSE+I, Exchange MVP

Hi All Deleting AD account leads to new SID and user logon would affected in the environment where single sign is applicable. For the safer side i would suggest to export the mailbox to PST, disable the mailbox create a new one at desired location and import all data. Thanks Prem P Rana MCSA Messaging 2003 MCSE 2003 Server MCTS MCITP Exchange 2007, 2010 Gurgaon, India Thanks Prem Rana * MCP,MCSE MCSA Exchange 2003 MCTS, MCITP Exchange 2007,2010 *